# -*- mode: ruby -*-
# vi: set ft=ruby :

# Config value for js-centos Vagrantfile

# Note for adding additional config values:
# Ruby only allow Constants or Class variable across files. Constants is automatically 
# defined by having the name in all capital letters. So in order for Vagrantfile to
# get the value from this file, the key/name must be ALL_CAPS

## Box Source
# 
# The office location to import the box from. This is to avoid PG office downloading box
# from KL office or vice versa. Currently supported values are:
#
# 'KL' : KL Office
# 'PG' : PG Office
#
# UPPERCASE ONLY
VM_BOX_SOURCE = 'KL'

## App name
#
# The app required to in the VM. Specifiying this and the VM will checkout/clone
# related app codes as well as set up necessary configuration for the application
# to run in VM.
#
# 'jobseekers'  : For Jobseekers (MyJS/JobSearch/etc)
# 'papi'        : For PAPI 
#
# 'all'         : All of Above
#
# 'baas'        : For Baas Worker (Not included in 'all' due to differcent PHP version)
# 'none'        : For an empty VM
#
VM_APP = 'none'


## Path for your development folders
#
# This will be the default path for all your codes that should shared to the VM. It 
# will be mapped to /var/www/seekasia.com/ in the VM. The application specified in
# VM_APP above will have its codes and related artefacts placed in this directory 
# too.
#
# Please use forward slash '/' even for Windows path. Drive letters are legitimate
# such as 'C:/mylocaldev'. Avoid placing the codes directly inside the Vagrant 
# folder, as this may cause some unnecessary mount overhead.
#
# Default: ../../src, which is a src folder outside the git repository path.
#

VM_SRC_PATH = '../../src' 

## Amount of CPU for VM
#
# VM will share CPU cores with host. So it won't take away existing core. Hence,
# the recommended value below.

VM_CPU = 4 # Recommended Value = The exact amount of Cores your host CPU has

## Amount of RAM for VM
#
# This is kind of a "reserved" amount for VM. The actual RAM usage for VM is exactly 
# the amount the VM is using at that point. Setting this value will not instantly
# take out the amount of RAM from your host, but potentially cap the RAM at that amount.
#
# Swap will occur in either your host or VM depending on which side is ran out of memory.
# This will cause a huge (noticeable) performance hit if it happens

VM_RAM = 2048 # Recommended Value = 1/4 of your host physical RAM

